I get a reproduceable BLUE SCREEN when starting Sysinternal's "Process Monitor" (date 2006). No process or library is listed in the Technical information.*** STOP: 0x0000007F (...)This happens on a fresh installation of Windows 7 64-bit running on a (bootcamped) Macbook Pro (late 2008) with current NVidia and Broadcom drivers being installed.

Sorry, I don't know if I understand correctly, There is a build of Process Monitor date 12-10-2008 and number 2.03 and I cannot reproduce your blue screen in a x64 installation with broadcom and nvdia drivers. It's same versin that you're trying?"The only thing necessary for the triumph of evil is for good men to do nothing"

Thanks forreplying.I'm trying the old Sysinternals' build 1.01, not the current Microsoft one. Shouldn't be causing any Blue Screens nevertheless.

It's another point of view, but sincerely, I think, there are many changes on Windows Vista and W.Seven, and an old version could causes a bluescreen, why not?I'll try if possible with that old version. see you."The only thing necessary for the triumph of evil is for good men to do nothing"

Well, nothing should ever cause a BLUE SCREEN to begin with especially if it is a user mode application and not a kernel mode driver.The same application runs flawlessly on both XP and Vista 32-bit on another computer. I cannot check Vista 64-bit and W7 32-bit at the moment. I also find it worrying that no specific module is listed in the BLUE SCREEN message.Thecurrent version (2.02 in german) does not cause a BLUE SCREEN, but nevertheless there's something at least strange happening under the hood.